Interface between 3gpp networks and 3gpp2 networks for wap text messaging

ABSTRACT

Systems and methods are disclosed for interworking WAP text messages between 3GPP and 3GPP2 networks. One embodiment comprises a system that receives a WAP text message from a sending entity that supports 3GPP standards, where the WAP text message is in a 3GPP format. The system determines that a receiving entity for the WAP text message supports 3GPP2 standards, and converts the WAP text message from the 3GPP format to a 3GPP2 format. The system then transmits the WAP text message in the 3GPP2 format to the receiving entity.

FIELD OF THE INVENTION

The invention is related to the field of communications and, inparticular, to interfacing 3GPP networks and 3GPP2 networks for textmessaging.

BACKGROUND

Text messaging has become a popular mode of communication in many mobile(or wireless) networks. One example of text messaging is Short MessageService (SMS), which is a set of communication protocols allowing theexchange of short text messages (i.e., 160 characters or less) betweendevices. While the term “text message” traditionally referred totext-only messages sent using SMS, it has been extended to includemultimedia messages, such as images, video, sound content, etc. Themultimedia messages may be sent using Multimedia Message Service (MMS)protocol. Often times, mobile users more frequently use text messagingfor communication than voice calls.

Wireless Application Protocol (WAP) is a suite of protocols that may beused in conjunction with text messaging protocols (e.g., SMS) to provideinteractive sessions in mobile devices. Using WAP over SMS, for example,a user may send an SMS message that includes a Universal ResourceLocator (URL). When the SMS message is received by the recipient, therecipient's device displays a URL link that the recipient may select toview the corresponding website.

The 3^(rd) Generation Partnership Project (3GPP) is an organization thatdefines standards for telecommunications based on Global System forMobile Communications (GSM) specifications. The 3^(rd) GenerationPartnership Project 2 (3GPP2) is another organization that definesstandards for telecommunications based on CDMA2000 specifications. The3GPP and 3GPP2 both define standards for text messaging, including textmessaging using WAP. The 3GPP standards are different than the 3GPP2standards, which makes WAP text messaging between 3GPP and 3GPP2networks difficult if not impossible.

SUMMARY

Embodiments described herein interwork WAP text messages between a 3GPPnetwork and a 3GPP2 network. A system described herein is able totranslate WAP text messages from a 3GPP format to a 3GPP2 format, andvice-versa. This allows service providers to deliver WAP text messagingseamlessly across different technology networks, such as a Global Systemfor Mobile Communications (GSM) network, a CDMA2000 network, a Long TermEvolution (LTE) network, an IP Multimedia Subsystem (IMS) network, etc.

One embodiment comprises a system that handles a WAP text message. Thesystem includes an interface operable to receive a WAP text message froma sending entity that supports 3GPP standards, where the WAP textmessage is in a 3GPP format. The system further includes a controlleroperable to determine that a receiving entity for the WAP text messagesupports 3GPP2 standards, and to convert the WAP text message from the3GPP format to a 3GPP2 format. The interface is further operable totransmit the WAP text message in the 3GPP2 format to the receivingentity.

In another embodiment, the interface is operable to receive a WAP textmessage from a sending entity that supports 3GPP2 standards, where theWAP text message is in a 3GPP2 format. The controller is furtheroperable to determine that a receiving entity for the WAP text messagesupports 3GPP standards, and to convert the WAP text message from the3GPP2 format to a 3GPP format. The interface is further operable totransmit the WAP text message in the 3GPP format to the receivingentity.

Other exemplary embodiments may be described below.

DESCRIPTION OF THE DRAWINGS

Some embodiments of the present invention are now described, by way ofexample only, and with reference to the accompanying drawings. The samereference number represents the same element or the same type of elementon all drawings.

FIG. 1 illustrates a communication system in an exemplary embodiment.

FIG. 2 is a flow chart illustrating a method of converting a WAP textmessage in an exemplary embodiment.

FIG. 3 is a flow chart illustrating another method of converting a WAPtext message in an exemplary embodiment.

FIG. 4 illustrates a 3GPP text message in an exemplary embodiment.

FIG. 5 illustrates a 3GPP2 text message in an exemplary embodiment.

DESCRIPTION OF EMBODIMENTS

The figures and the following description illustrate specific exemplaryembodiments of the invention. It will thus be appreciated that thoseskilled in the art will be able to devise various arrangements that,although not explicitly described or shown herein, embody the principlesof the invention and are included within the scope of the invention.Furthermore, any examples described herein are intended to aid inunderstanding the principles of the invention, and are to be construedas being without limitation to such specifically recited examples andconditions. As a result, the invention is not limited to the specificembodiments or examples described below, but by the claims and theirequivalents.

FIG. 1 illustrates a communication system 100 in an exemplaryembodiment. Communication system 100 includes a 3GPP network 110, agateway system 120, and a 3GPP2 network 130. 3GPP network 110 comprisesany network that communicates based on 3GPP standards. For example, 3GPPnetwork 110 may comprise a GSM network, a Universal MobileTelecommunications System (UMTS) network, an LTE network, an IMSnetwork, etc. 3GPP network 110 includes 3GPP entity 112. 3GPP entity 112comprises any server, node, device, etc., that communicates based on3GPP standards. For example, 3GPP entity 112 may comprise a mobiledevice or an SMS Center (SMSC) in a GSM network or a UMTS network.

3GPP2 network 130 comprises any network that communicates based on 3GPP2standards. For example, 3GPP2 network 130 may comprise a CDMA2000network or an IMS network. 3GPP2 network 130 includes a 3GPP2 entity132. 3GPP2 entity 132 comprises any server, node, device, etc., thatcommunicates based on 3GPP2 standards. For example, 3GPP2 entity 132 maycomprise a mobile device or an SMSC in a CDMA2000 network.

3GPP network 110 and 3GPP2 network 130 offer text messaging to theirsubscribers (not shown). In the embodiments described below, WAPmessaging is used in conjunction with text messaging. 3GPP network 110and 3GPP2 network 130 provide WAP text messaging in 3GPP format and3GPP2 format, respectively. Because the 3GPP format for WAP textmessaging and the 3GPP2 format for WAP text messaging are different,gateway system 120 is implemented between 3GPP network 110 and 3GPP2network 130. Gateway system 120 comprises any system or server operableto interwork WAP text messages between a 3GPP format and a 3GPP2 format,and vice-versa. Gateway system 120 may be a stand-alone device asillustrated in FIG. 1. Alternatively, gateway system 120 may beimplemented in a text messaging element in either network, such as in anSMSC, an IP-SM-GW, an SM-IC-GW, an LTE-SM-GW, etc.

Assume for one embodiment that 3GPP entity 112 sends a WAP text messagethat is intended for 3GPP2 entity 132. The WAP text message isencapsulated in a signaling message, such as a MAP ForwardSM or a SIPMESSAGE (RP-DATA). The WAP text message may be Mobile Originated (MO),Mobile Terminated (MT), Application Originated (AO), or ApplicationTerminated (AT). Before the WAP text message can be sent to 3GPP2 entity132, the WAP text message is sent to gateway system 120 for conversionto the proper format. The operation of gateway system 120 is describedfurther in FIG. 2.

FIG. 2 is a flow chart illustrating a method 200 of converting a WAPtext message in an exemplary embodiment. The steps of method 200 will bedescribed with reference to gateway system 120 in FIG. 1, but thoseskilled in the art will appreciate that method 200 may be performed inother networks and systems. The steps of the flow charts describedherein are not all inclusive and may include other steps not shown. Thesteps may also be performed in an alternative order.

In step 202, interface 122 receives the WAP text message from 3GPPentity 112 (which is the sending entity). The WAP text message is in3GPP format. In step 204, controller 124 determines that 3GPP2 entity132 (which is the receiving entity) supports 3GPP2 standards instead of3GPP standards. For example, gateway system 120 may maintain its owndatabase for the mode type used by the receiving entity. If thereceiving entity is a handset, then controller 124 may access the localdatabase to determine which standards the handset supports (includingsingle or dual mode types). Controller 124 may also query a subscriberdatabase, such as a Home Subscriber Server (HSS) or a Home LocationRegister (HLR) to check the registration status of the handset todetermine which network the handset is in and which mode the handset iscurrently operating in. By determining the standard used by the handset,controller 124 is able to determine whether to convert the WAP textmessage from one standard to another standard.

Controller 124 then converts the WAP text message from 3GPP format to3GPP2 format in step 206. After conversion, interface 122 transmits theWAP text message to 3GPP2 entity 132 in step 208. Because the WAP textmessage is converted to the appropriate format, 3GPP2 entity 132 is ableto handle the WAP text message. For instance, if 3GPP2 entity 132 is amessage center, such as an SMSC, then it is able to handle delivery ofthe WAP text message. If 3GPP2 entity 132 is a mobile device, then it isable to process the WAP text message for display to an end user.

To convert the WAP text message from 3GPP format to 3GPP2 format (step206), controller 124 parses the WAP text message in 3GPP format toidentify parameters for the WAP text message. For example, if the 3GPPWAP text message is a MAP message, then controller 124 identifies UserData Header (UDH) parameters of the Short Message-Transfer Layer(SM-TL). Controller 124 then maps the UDH parameters to User Dataparameters of the Teleservice layer and/or Transport layer (in 3GPP2format).

Assume for another embodiment that 3GPP2 entity 132 sends a WAP textmessage that is intended for 3GPP entity 112. Before the WAP textmessage can be sent to 3GPP entity 112, the WAP text message is sent togateway system 120 for conversion to the proper format. The operation ofgateway system 120 is described further in FIG. 3.

FIG. 3 is a flow chart illustrating another method 300 of converting aWAP text message in an exemplary embodiment. The steps of method 300will be described with reference to gateway system 120 in FIG. 1, butthose skilled in the art will appreciate that method 200 may beperformed in other networks and systems.

In step 302, interface 122 receives the WAP text message from 3GPP2entity 132 (which is the sending entity). The WAP text message is in3GPP2 format. In step 304, controller 124 determines that 3GPP entity112 (which is the receiving entity) supports 3GPP standards instead of3GPP2 standards. Therefore, controller 124 converts the WAP text messagefrom 3GPP2 format to 3GPP format in step 306. After conversion,interface 122 transmits the WAP text message to 3GPP entity 112 in step308. Because the WAP text message was converted to the appropriateformat, 3GPP entity 112 is able to handle the WAP text message.

To convert the WAP text message from 3GPP2 format to 3GPP format (step306), controller 124 parses the WAP text message in 3GPP2 format toidentify Teleservice layer and/or Transport layer parameters. Controller124 then maps the Teleservice layer and Transport layer parameters toSM-TL parameters in the 3GPP format.

Format conversion is described in more detail below. Text messages areencoded as a header and a payload in a Protocol Description Unit (PDU).FIG. 4 illustrates a 3GPP text message 400 in an exemplary embodiment.Text message 400 includes header 410 and payload 420. Header 410includes metadata for transporting the text message in the Short MessageTransport Layer (SM-TL), such as an originating address for the textmessage, a destination address for the text message, etc. Payload 420includes the actual content for the text message.

When WAP is implemented with 3GPP text messaging, a User Data Header(UDH) 422 is inserted in payload 420 of the text message. Therefore,payload 420 comprises UDH 422 followed by the content of the textmessage. UDH 422 includes the data for the WAP function being used inthe text message. For example, if the WAP function is a “PUSH”, then thedata in the UDH 422 indicates destination and source ports for the PUSHoperation.

UDH 422 includes a User Data Header Length (UDHL) parameter 430 and oneor more Information Elements (IE) 432-433. Each Information Element (IE)432 includes the following sub-parameters (typically in octets):Information Element Identifier (IEI) 442, Information Element DataLength (IEDL) 444, and Information Element Data (IED) 446. IEI 442indicates the type of data included in an IED 446. For example, if IEI442 is set to “05”, then the IED 446 includes source port informationand destination port information for WAP applications. If IEI 442 is setto “00”, then IED 446 includes information for concatenation of a textmessage (i.e., a long text message (over 160 characters) is segmentedand sent as multiple messages).

The following illustrates an example of an IE 432:

05 04 0B 84 23 FO

In this IE 432, the “05” octet is IEI 442, which indicates that portaddressing information is included in the IED 446. The “04” octet isIEDL 444, which indicates that the data length is four octets. The “0B84” octets and “23 FO” octets are IED 446. The “0B 84” octets indicatethe destination port, which is commonly used for a WAP PUSH operation.The “23 FO” octets indicate the source port.

FIG. 5 illustrates a 3GPP2 text message 500 in an exemplary embodiment.Text message 500 includes a header 510 and a payload 520. As above,header 510 includes metadata for transporting the text message. In thisembodiment, header 510 includes a Teleservice ID parameter 512 that ispart of the Transport Layer in the 3GPP2 SMS protocol stack. When thetext message includes a WAP operation, then the Teleservice ID is set to“4100”. Payload 520 includes a User Data parameter 522 that is part ofthe Teleservice Layer in the 3GPP2 SMS protocol stack. When WAP isimplemented with 3GPP2 text messaging, the WAP information is insertedin User Data parameter 522. User Data parameter 522 includes a CHARifield structure 530, which includes the following fields: message type(MSG_TYPE) 532, total number of segments (TOTAL_SEGMENTS) 534, segmentnumber (SEGMENT_NUMBER) 536, source port (SOURCE_PORT) 538, destinationport (DESTINATION_PORT) 540, and the content of the text message (DATA)542.

As is evident in comparing FIG. 4 and FIG. 5, the text message formatfor 3GPP WAP and for 3GPP2 WAP are different. Therefore, to convertbetween 3GPP format and 3GPP2 format, a mapping is described hereinbetween the parameters of the 3GPP UDH and the fields of the 3GPP2 UserData (Teleservice Layer). The term “parameter” and “field” are usedinterchangeably herein.

Most WAP text messages are sent using WAP Datagram Protocol (WDP). Table1 illustrates an exemplary mapping between 3GPP and 3GPP2 for WDPmessages.

TABLE 1 CHARi Field Structure Length (bits) GSM Field MSG_TYPE 8 Testequal to (=‘00000000’) ‘00000000’ for WDP TOTAL_SEGMENTS 8 Part of IEI0, in UDH SEGMENT_NUMBER 8 Part of IEI 0, in UDH SOURCE_PORT 16 Part ofIEI 5, in UDH DESTINATION_PORT 16 Part of IEI 5, in UDH DATA (NUM_FIELDS− TP-User-Data content, 7) * 8 after the UDHBased on Table 1, TOTAL_SEGMENTS field 534 of the 3GPP2 User Dataparameter is mapped to an Information Element of the 3GPP UDH having anIEI set to “00” (e.g., concatenated text message). More particularly,the TOTAL_SEGMENTS field 534 is mapped to the IED parameter in this IEthat indicates the number of segments in a concatenated message.SEGMENT_NUMBER field 536 of the 3GPP2 User Data parameter is also mappedto the Information Element having an IEI set to “00”. More particularly,the SEGMENT_NUMBER field 536 is mapped to the IED parameter in this IEthat indicates the segment number of a concatenated message. TheSOURCE_PORT field 538 of the 3GPP2 User Data parameter is mapped to theInformation Element having an IEI set to “05”. More particularly, theSOURCE_PORT field 538 is mapped to the IED parameter in this IE thatindicates the source port number. The DESTINATION_PORT field 540 of the3GPP2 User Data parameter is mapped to the Information Element having anIEI set to “05”. More particularly, the DESTINATION_PORT field 540 ismapped to the IED parameter in this IE that indicates the destinationport number. The DATA field 542 of the 3GPP2 User Data parameter ismapped to the TP-User-Data parameter that follows the UDH.

Wireless Control Message Protocol (WCMP) provides an error reportingmechanism for the WDP. It can also be used for diagnostics andinformational purposes. Table 2 illustrates an exemplary mapping between3GPP and 3GPP2 for WDP messages:

TABLE 2 CHARi Field Structure Length (bits) GSM Field MSG_TYPE 8 Testequal to (=‘00000001’) ‘00000001’ for WCMP WCMP_MESSAGE (NUM_FIELDS −Add IEI 09 to the 1) * 8 UDH, and include the WCMP message in IED

Based on Table 2, the WCMP_MESSGE field of the 3GPP2 User Data parameteris mapped to an Information Element of the 3GPP UDH having an IEI set to“09”. More particularly, the WCMP_MESSGE field is mapped to the IEDparameter in this IE.

The 3GPP and 3GPP2 formats have different user data lengths. Duringconversion from 3GPP2 format to 3GPP format, the unmatched lengthlimitation could cause problems. One option is to trim or dropcharacters in the 3GPP2 WAP text message to meet the size limitation ofthe 3GPP format. Another option is to segment the 3GPP2 WAP text messageto handle the different user data lengths between the formats. Forexample, assume that controller 124 receives a 3GPP2 WAP text message.If the length of the 3GPP2 WAP text message exceeds the maximum SMSlength (e.g., 140 octets) for the 3GPP format, then controller 124segments the 3GPP2 WAP text message into multiple 3GPP WAP textmessages. Controller 124 then sends the multiple segments to thereceiving entity.

When a 3GPP2 WAP text message is segmented into multiple 3GPP WAP textmessages, only the first segment carries the port numbers. However, 3GPPWAP requires the port number to be in each segment, because thedifferent segments of the same WAP text message could go to differentSMS gateways. One solution to this problem is to use the following IEIsfor encoding of User Data Header (UDH) in the 3GPP WAP text message:

1. IEI “00” (8-bit reference number) or IEI “08” (16-bit referencenumber) depending on the message reference value, for concatenationinformation if the WAP text message is a multi-segment message. Formulti-segment WAP text message, these IEI values are encoded in eachsegment of the WAP text message.

2. IEI “05” (16-bit address) for SOURCE_PORT and DESTINATION_PORT forthe incoming SMPP WAP text message. For a single segment message or forthe first segment of a multi-segment WAP text message, controller 124uses the port numbers from the incoming SMPP message from the followingsources: TLVs ‘source_port’ and ‘destination_port’ if present in themessage, or WAP WDP message payload (first 4 octets). For each of thesubsequent segments of a multi-segment WAP text message, controller 124uses the port numbers from the TLVs (‘source_port’ and‘destination_port’) if the TLVs are present in the SMPP message for thatsegment. If these TLVs are not present in a specific segment, thencontroller 124 does not encode the port numbers in the 3GPP UDH for thatsegment.

If the SMPP message is multi-segment message, then controller 124 usesthe TP-MMS parameter to indicate more messages to send for efficientdelivery of the segmented WAP text message. The TP-DCS parameter may beset to 8-bit data since the data_coding in the incoming WAP text messageis octet unspecified.

When converting from 3GPP format to 3GPP2 format, controller 124 mayconvert multiple segments of a 3GPP WAP text message into a singlesegment in 3GPP2 format. Thus, controller 124 receives a segment of theWAP text message in 3GPP format. Controller 124 determines that the WAPtext message is one of multiple segments for this message. Therefore,controller 124 waits until all segments are received for the WAP textmessage. Controller 124 then aggregates the payloads of the segments,and converts the WAP text message from 3GPP format to 3GPP2 format.After aggregation and conversion, controller 124 sends the WAP textmessage in 3GPP2 format to the receiving entity.

The embodiments described above allow service providers to deliver WAPtext messages seamlessly across different technology networks (e.g.,CDMA2000, GSM, UMTS, IMS, LTE, etc.).

The following examples illustrate conversion between 3GPP format and3GPP2 format. Assume in one example that 3GPP entity 112 in FIG. 1 is amobile device that originates a WAP SMS message in 3GPP format. The WAPSMS message may be encapsulated in either a MAP mo-ForwardSM(SMS-SUBMIT), or a SIP MESSAGE with RP-DATA for SMS-SUBMIT. Because thisis a WAP message, the TP-User-Data parameter of the WAP SMS messageincludes a UDH. The UDH includes an Information Element with an IEI setto “05” for source/destination ports. The UDH also includes anInformation Element with an IEI set to “09” for WCMP. Gateway system 120detects that 3GPP2 entity 132 only supports 3GPP2 format. Thus, gatewaysystem 120 converts the 3GPP WAP MO SMS message into a 3GPP2 WAP MO SMSmessage by mapping the UDH parameters to 3GPP2 User Data parameters. Forinstance, gateway system 120 maps the IED for an Information Element(IEI=“05”) to the SOURCE_PORT parameter and DESTINATION_PORT parameterof the 3GPP2 User Data (see Table 1). Gateway system 120 then forwardsthe WAP MO SMS message to 3GPP2 entity 132 in 3GPP2 format.

In another example, assume that 3GPP2 entity 132 is a mobile device thatoriginates a WAP WDP or WAP WCMP SMS message with the TeleserviceID=4100. The 3GPP2 WAP SMS message is received by gateway system 120. Inthis example, gateway system 120 may be implemented in an SMS-IC-GW, anIP-SM-GW, an LTE-SMS-GW, etc. The receiving entity 112 may comprise anSMSC or SMS GW. Gateway system 120 detects that receiving entity 112only supports 3GPP format. Thus, gateway system 120 convert the 3GPP2WAP SMS message into either a 3GPP MAP mo-ForwardSM (SMS-SUBMIT) or aSIP MESSAGE encapsulated RP-DATA for SMS-SUBMIT. In either case, gatewaysystem 120 maps 3GPP2 User Data parameters with TP-User Data in the MAPmo-ForwardSM (SMS-SUBMIT) or a SIP MESSAGE. For instance, gateway system120 maps the SOURCE_PORT parameter and DESTINATION_PORT parameter to anInformation Element with an IEI set to “05” for source/destination ports(see Table 1). Gateway system 120 then forwards the WAP MO SMS messageto 3GPP entity 112 in 3GPP format.

Any of the various elements shown in the figures or described herein maybe implemented as hardware, software, firmware, or some combination ofthese. For example, an element may be implemented as dedicated hardware.Dedicated hardware elements may be referred to as “processors”,“controllers”, or some similar terminology. When provided by aprocessor, the functions may be provided by a single dedicatedprocessor, by a single shared processor, or by a plurality of individualprocessors, some of which may be shared. Moreover, explicit use of theterm “processor” or “controller” should not be construed to referexclusively to hardware capable of executing software, and mayimplicitly include, without limitation, digital signal processor (DSP)hardware, a network processor, application specific integrated circuit(ASIC) or other circuitry, field programmable gate array (FPGA), readonly memory (ROM) for storing software, random access memory (RAM), nonvolatile storage, logic, or some other physical hardware component ormodule.

Also, an element may be implemented as instructions executable by aprocessor or a computer to perform the functions of the element. Someexamples of instructions are software, program code, and firmware. Theinstructions are operational when executed by the processor to directthe processor to perform the functions of the element. The instructionsmay be stored on storage devices that are readable by the processor.Some examples of the storage devices are digital or solid-statememories, magnetic storage media such as a magnetic disks and magnetictapes, hard drives, or optically readable digital data storage media.

Although specific embodiments were described herein, the scope of theinvention is not limited to those specific embodiments. The scope of theinvention is defined by the following claims and any equivalentsthereof.

1. A system comprising: an interface operable to receive a WirelessApplication Protocol (WAP) text message from a sending entity thatsupports 3^(rd) Generation Partnership Project (3GPP) standards, whereinthe WAP text message is in a 3GPP format; and a controller operable todetermine that a receiving entity for the WAP text message supports3^(rd) Generation Partnership Project 2 (3GPP2) standards, and toconvert the WAP text message from the 3GPP format to a 3GPP2 format; theinterface is further operable to transmit the WAP text message in the3GPP2 format to the receiving entity.
 2. The system of claim 1 wherein:the controller is further operable to parse the WAP text message in 3GPPformat to identify User Data Header (UDH) parameters, and to map the UDHparameters to User Data parameters of the 3GPP2 Teleservice Layer. 3.The system of claim 2 wherein: the controller is further operable to mapInformation Element Data from an Information Element having anInformation Element Identifier set to “05” to a source port parameterand a destination port parameter in the Teleservice Layer.
 4. The systemof claim 2 wherein: the controller is further operable to mapInformation Element Data from an Information Element having anInformation Element Identifier set to “00” to a number-of-segmentsparameter and a segment-number parameter in the Teleservice Layer. 5.The system of claim 1 wherein: the controller is further operable toreceive multiple segments for the WAP text message in 3GPP format, toaggregate the multiple segments into a single segment, and to convertthe single segment of the WAP text message to the 3GPP2 format.
 6. Amethod comprising: receiving a Wireless Application Protocol (WAP) textmessage from a sending entity that supports 3^(rd) GenerationPartnership Project (3GPP) standards, wherein the WAP text message is ina 3GPP format; determining that a receiving entity for the WAP textmessage supports 3^(rd) Generation Partnership Project 2 (3GPP2)standards; converting the WAP text message from the 3GPP format to a3GPP2 format; and transmitting the WAP text message in the 3GPP2 formatto the receiving entity.
 7. The method of claim 6 wherein converting theWAP text message from the 3GPP format to a 3GPP2 format comprises:parsing the WAP text message in 3GPP format to identify User Data Header(UDH) parameters; and mapping the UDH parameters to User Data parametersof the 3GPP2 Teleservice Layer.
 8. The method of claim 7 wherein mappingthe UDH parameters comprises: mapping Information Element Data from anInformation Element having an Information Element Identifier set to “05”to a source port parameter and a destination port parameter in theTeleservice Layer.
 9. The method of claim 7 wherein mapping the UDHparameters comprises: mapping Information Element Data from anInformation Element having an Information Element Identifier set to “00”to a number-of-segments parameter and a segment-number parameter in theTeleservice Layer.
 10. The method of claim 6 further comprising:receiving multiple segments for the WAP text message in 3GPP format;aggregating the multiple segments into a single segment; and convertingthe single segment of the WAP text message to the 3GPP2 format.
 11. Asystem comprising: an interface operable to receive a WirelessApplication Protocol (WAP) text message from a sending entity thatsupports 3^(rd) Generation Partnership Project 2 (3GPP2) standards,wherein the WAP text message is in a 3GPP2 format; and a controlleroperable to determine that a receiving entity for the WAP text messagesupports 3^(rd) Generation Partnership Project (3GPP) standards, and toconvert the WAP text message from the 3GPP2 format to a 3GPP format; theinterface is further operable to transmit the WAP text message in the3GPP format to the receiving entity.
 12. The system of claim 11 wherein:the controller is further operable to parse the WAP text message in3GPP2 format to identify User Data parameters of the 3GPP2 TeleserviceLayer, and to map the User Data parameters to User Data Header (UDH)parameters of the Mobile Application Part (MAP) Short Message TransportLayer (SM-TL).
 13. The system of claim 12 wherein: the controller isfurther operable to map a source port parameter and a destination portparameter in the Teleservice Layer to Information Element Data from anInformation Element having an Information Element Identifier set to“05”.
 14. The system of claim 12 wherein: the controller is furtheroperable to map a number-of-segments parameter and a segment-numberparameter in the Teleservice Layer to Information Element Data from anInformation Element having an Information Element Identifier set to“00”.
 15. The system of claim 11 wherein: the controller is furtheroperable to determine that after conversion, a length of the WAP textmessage exceeds a length limit in the 3GPP format, and to segment theWAP text message into multiple segments in the 3GPP format.
 16. A methodcomprising: receiving a Wireless Application Protocol (WAP) text messagefrom a sending entity that supports 3^(rd) Generation PartnershipProject 2 (3GPP2) standards, wherein the WAP text message is in a 3GPP2format; determining that a receiving entity for the WAP text messagesupports 3^(rd) Generation Partnership Project (3GPP) standards;converting the WAP text message from the 3GPP2 format to a 3GPP format;and transmitting the WAP text message in the 3GPP format to thereceiving entity.
 17. The method of claim 16 wherein converting the WAPtext message from the 3GPP2 format to a 3GPP format comprises: parsingthe WAP text message in 3GPP2 format to identify User Data parameters ofthe 3GPP2 Teleservice Layer; and mapping the User Data parameters toUser Data Header (UDH) parameters of the Mobile Application Part (MAP)Short Message Transport Layer (SM-TL).
 18. The method of claim 17wherein mapping the User Data parameters comprises: mapping a sourceport parameter and a destination port parameter in the Teleservice Layerto Information Element Data from an Information Element having anInformation Element Identifier set to “05”.
 19. The method of claim 17wherein mapping the User Data parameters comprises: mapping anumber-of-segments parameter and a segment-number parameter in theTeleservice Layer to Information Element Data from an InformationElement having an Information Element Identifier set to “00”.
 20. Themethod of claim 16 further comprising: determining that afterconversion, a length of the WAP text message exceeds a length limit inthe 3GPP format; and segmenting the WAP text message into multiplesegments in the 3GPP format.